Transmission method and apparatus in tdd-fdd joint system

ABSTRACT

The present invention provides a transmission method and apparatus in a TDD-FDD joint system. In an embodiment of cross-carrier scheduling, an HARQ time sequence of a PUSCH on a scheduled CC complies with a time sequence of a TDD system, and an HARQ time sequence of a PDSCH on the scheduled CC complies with a time sequence of an FDD system; if an uplink reference frame structure on the scheduled CC is #0, uplink-scheduling DCI of the scheduled CC comprises ULI/DAI bits; and if the uplink reference frame structure on the scheduled CC is one of #1 to #6, the uplink-scheduling DCI of the scheduled CC does not comprise the ULI/DAI bits. By using the technical solutions provided in the present invention, redundant overheads of the DCI are reduced, the coverage of the DCI is enlarged, and meanwhile, the compatibility with an existing system is kept to the greatest degree in the present invention.

BACKGROUND

1. Technical Field

The disclosure is related to a subframe scheduling scheme in the TimeDivision Duplex—Frequency Division Duplex (TDD-FDD) joint system, andmore particular to a timing scheme for the cross-carrier scheduling inthe TDD-FDD Long Term Evolution (LTE) system, and specifically to atransmission method and device in a TDD-FDD joint system.

2. Related Art

The traditional LTE (Long Term Evolution) system of 3rd GenerationPartner Project (3GPP) defines two duplex modes, which are FrequencyDivision Duplex (FDD) system and Time Division Duplex (TDD) systemrespectively. FDD adopts frame structure 1, while TDD adopts framestructure 2. The difference between FDD and TDD lies in that eachsubframe of FDD frame configuration is 1 millisecond, while the TDDsystem defines 1 to 2 special subframes in one frame (10 subframes). Thespecial subframes are composed of a downlink synchronous time slot, aguard period and an uplink synchronization time slot. 3GPP defines theframe configuration for the TDD-LTE system, as shown in Table 1, inwhich D indicates downlink subframe, U indicates uplink subframe, and Sindicates special subframe.

TABLE 1 TDD LTE Frame Configuration Downlink- TDD to-Uplink FrameSwitch-point Subframe Index No. Configuration Periodicity 0 1 2 3 4 5 67 8 9 0  5 ms D S U U U D S U U U 1  5 ms D S U U D D S U U D 2  5 ms DS U D D D S U D D 3 10 ms D S U U U D D D D D 4 10 ms D S U U D D D D DD 5 10 ms D S U D D D D D D D 6  5 ms D S U U U D S U U D

3GPP further defines the uplink scheduling delay k for thecross-subframe, as shown in Table 2. The meaning of k is: for DownlinkControl Information (DCI) used for uplink scheduling in the downlinksubframe n, the scheduling subframe is on the subframe n+k. It should benoted that for TDD frame configuration #0, k is as shown in Table 2, or7, or as shown in Table 2 and 7 simultaneously, which may be configuredvia the uplink index (ULI) in DCI.

TABLE 2 Scheduling Parameter k of the uplink subframe in TDD LTE TDDFrame Subframe Index No. Configuration 0 1 2 3 4 5 6 7 8 9 0 4 6 4 6 1 64 6 4 2 4 4 3 4 4 4 4 4 4 5 4 6 7 7 7 7 5

When the Physical Uplink Shared Channel (PUSCH) is scheduled accordingto the frame configuration #0 (for example, the uplink reference DL/ULframe structure in the above scheme is #0), thetwo-bit uplink index(ULI) is defined in the DCI to indicate the index of the uplink subframescheduled by the DCI. It should be noted that the two bits are used forDownlink Assignment Index (DAI) instead of being used as ULI for thenon-zero frame configurations. That is, the two bits are used toindicate the amount of Physical Downlink Shared Channel (PDSCH)represented by the uplink ACK/NACK corresponding to the DCI. For theACK/NACK reported on the uplink subframe n, the targeting PDSCH can onlybe PDSCH indicated by DCI sent on the subframe n−k, wherein k belongs tothe subframe set K, as defined in Table 3.

TABLE 3 Downlink Associating Subframe Set K TDD Frame Config- SubframeIndex n uration 0 1 2 3 4 5 6 7 8 9 0 — — 6 — 4 — — 6 — 4 1 — — 7,6 4 —— — 7,6 4 — 2 — — 8, 7, 4, 6 — — — — 8, 7, — — 4, 6 3 — — 7, 6, 11 6, 55, 4 — — — — — 4 — — 12, 8, 7, 11 6, 5, 4, — — — — — — 7 5 — — 13, 12,9, 8, — — — — — — — 7, 5, 4, 11, 6 6 — — 7 7 5 — — 7 7 —

In LTE system, the communication between the base station and the userequipment (UE) is scheduled by Physical Downlink Control Channel(PDCCH). The information transmitted on PDCCH is Downlink ControlInformation (DCI). Further, DCI is divided into uplink-scheduling DCIand downlink-scheduling DCI. The former schedules the UE to transmituplink data, and the latter schedules the UE to receive downlink data.As of 3GPP Release 11 (R11), DCI formats {0, 4} are foruplink-scheduling DCI, DCI formats {1, 1A, 1B, 1C, 1D, 2, 2A, 2B, 2C,2D} are for downlink-scheduling DCI, and DCI formats {3, 3A} are foradjusting uplink transmission power. For the TDD system, DCI includesadditional bits (that is the additional bits do not occur in FDDsystem). For example, Downlink Assignment Index (DAI) or Uplink Index(ULI) of two bits, sounding Reference Signal Request of one bit ofpartial DCI format (2B, 2C, 2D), or Hybrid Automatic Repeat Request(HARQ) process number of additional one bit. Therefore, under the samesystem configuration and DCI format, DCI in the TDD system usually hasadditional two to four bits compared to the DCI in FDD system.

In order to improve the peak rate of communication and provide greaterflexibility in scheduling, 3GPP introduces Carrier Aggregation (CA)technology, that is to allow UE to simultaneously receive and send dataon more than one carrier. When the UE is configured with more than onecarrier, one of the carriers is Primary Carrier Component (PCC), and theothers are Secondary Carrier Component (SCC). Further, the cross carrierscheduling technology is introduced to 3GPP, that is DCI has CarrierIndicator Field (CIF) of additionally three bits for indicating whichcandidate carrier is the carrier scheduled by DCI. The CIF value of PCCis fixed to 0. The system configures that whether the current DCIincludes CIF or not thorough the high layer signaling. The UE reads thehigh layer signaling on PCC to obtain the system information of PCC andSCC. The high layer signaling is Radio Resource Control (RRC) layersignaling.

The traditional CA is performed internally in the same duplex mode, thatis multiple TDD carriers are aggregated or multiple FDD carriers areaggregated. 3GPP RAN #60 plenary approved a newstudy item: LTE TDD-FDDJoint Operation, that is a UE may access TDD and FDD networksimultaneously to obtain higher communicate rate or better communicationexperience. One intuitive solution is to expand the tranditional carrieraggregation scheme to TDD-FDD Joint Operation, that is the carrieraggregation scheme is performed between TDD carrier and FDD carrier.

When a FDD carrier is adopted as scheduling CC, and a TDD carrier isadopted as scheduled CC, the timing of the cross carrier schedulingrequires special design. The scheduling timing includes uplinkscheduling timing and downlink scheduling timing. The uplink schedulingtiming includes the timing relationship among the various steps: thebase station transmits uplink-scheduling DCI, the UE transmits data onPUSCH according to the DCI, the base station transmits ACK/NACK onPhysical HARQ Indicator Channel (PHICH), and the UE transmits data onPUSCH according to the ACK/NACK. The downlink scheduling timing includesthe timing relationship of the following steps: the base stationtransmits the downlink-scheduling DCI and data, and the UE reportsuplink ACK/NACK.

SUMMARY

Taking into account the compatibility with the existing systems, oneintuitive idea is that when a FDD carrier is adopted as PCC and the TDDcarrier is adopted as SCC, the cross carrier downlink schedulingcomplies with FDD downlink scheduling timing and the cross carrieruplink scheduling complies with TDD uplink scheduling timing. However,through study the inventor discovers that many conflictions existbetween the payload size of TDD uplink-scheduling DCI and FDDdownlink-scheduling DCI. If it is solved by adding padding bits, therewould be more redundant bits. The present invention discloses technicalsolutions for the above mentioned problem in the LTE TDD-FDD jointsystem.

According to the transmission method used in UE for a TDD-FDD jointsystem, the method comprises the following steps:

Step A: receiving a first DCI on the subframe n on a first carrier,wherein the first carrier is a FDD downlink carrier, n is an integer,and the first DCI is the uplink-scheduling DCI; and

Step B: transmitting the uplink data on PUSCH of a second carrier in thesubframe n+k according to the scheduling of the first DCI, wherein thesecond carrier is a TDD carrier, k is the uplink scheduling delay of theuplink reference frame configuration of the second carrier on thesubframe n;

wherein for frame configuration #{0, 1, 2, 3, 4, 5, 6}, the first DCIcomprises the ULI/DAI bits only when the uplink reference frameconfiguration is configuration #0.

The uplink scheduling delay is an absolute value of the differencebetween the subframe index of the uplink-scheduling DCI and the subframeindex of the corresponding PUSCH transmission. In the FDD-LTE system,the uplink scheduling delay is 4. The FDD carrier is a carriersupporting the LTE system on the FDD band. The TDD carrier is a carriersupporting the LTE system on the TDD band. The uplink-scheduling DCImeans DCI format {0, 4}, and the potential DCI formats defined in thefuture 3GPP releases. The PUSCH scheduling on the second carrier that isperformed by the first carrier, the PHICH feedback, and the PUSCHretransmission comply with the timing relationship of the uplinkreference frame configuration of the second carrier. The configurationof the uplink reference frame configuration is to be further discussedby 3GPP. The uplink reference frame configuration of the second carriermay be one of the following:

Scheme 1: the frame configuration configured by System Information Block(SIB) of the second carrier;

Scheme 2: the frame configuration configured by the high layersignaling, wherein the high layer signaling includes Radio ResourceControl (RRC) layer signaling, Medium Access Control (MAC) layersignaling, etc.; and

Scheme 3: static configuration, that is the uplink reference frameconfiguration of the second carrier is fixed as for example the frameconfiguration #0.

The above Scheme 2 and Scheme 3 are only applicable for the enhancedInterference Management Traffic Adaptation (eIMTA)-supported secondcarrier. Scheme 1 is applicable for the non-eIMTA second carrier.

The uplink-scheduling DCI includes two ULI/DAI bits (being as ULI(uplink index) when the frame configuration is #0, and being as DAI(downlink assignment index) when the frame configuration is otherconfiguration), which are TDD unique bits, such that theuplink-scheduling DCI of TDD has additionally two bits comparing withthe DCI of FDD having the same format. ULI is used to indicate theuplink subframe scheduled by the uplink-scheduling DCI, and DAI is usedto indicate the amount of the downlink PDSCH associated with ACK/NACKtransmitted on the scheduled PUSCH.

Preferably, the Step A comprises the following step A1, and the Step Bcomprises the following Step B1:

Step A1: in the jth subframe before the subframe n+k of the secondcarrier, receiving at least one of the following:

PDSCH data;

PDCCH indicating SPS (Semi Persistent Scheduling) release;

EPDCCH indicating SPS release;

Step B1: transmitting ACK/NACK associating with the Step A1 on thePUSCH;

wherein j is an uplink scheduling delay of the FDD system, in which j is4.

The essence of this aspect of the present invention is that for thecross-carrier scheduling that the FDD carrier is a scheduling CC and theTDD carrier is a scheduled CC, downlink scheduling complies with FDDtiming. ACK/NACK associating with the PDSCH of at most one subframe canbe reported on Uplink PUSCH. Therefore, DAI bits in DCI are notrequired.

Preferably, the method further comprises the following steps:

Step C: for the uplink data, detecting the PHICH information in the sthsubframe after the subframe n+k on the first carrier, wherein s is thePHICH reporting delay corresponding to the uplink reference frameconfiguration;

Step D: transfering ACK information to higher layers when the PHICH isdetected as ACK, or when no PHICH is detected.

The essence of this aspect of the present invention is that for thecross-carrier scheduling that the FDD carrier is a scheduling CC and theTDD carrier is a scheduled CC, uplink scheduling complies with TDDtiming.

Preferably, a padding bit of the first DCI is added according to the LTEscheme, wherein the corresponding downlink DCI is counted according tothe payload size of the cross-carrier scheduling performed in the FDDsystem for the second carrier.

When the first DCI is DCI format 0, the first DCI and DCI 1A that ismapped onto the same searching space and used to schedule the secondcarrier should satisfy the requirement: the first DCI and the DCI 1Ahave the same bit number, and the bit number is not the value as shownin Table 4.

TABLE 4 Bit Number of Conflict Information {12, 14, 16, 20, 24, 26, 32,40, 44, 56}

One or more padding bit(s) with zero value shall be appended to thefirst DCI and the DCI 1A until the above requirement is satisfied. Whenthe first DCI is DCI format 0, and DCI 1B or DCI 1D that is mapped ontothe same searching space and used to schedule the second carrier has thesame bit number as the first DCI, one or more padding bits with 0 valueshall be appended to the DCI 1B or DCI 1D until the bit number of DCI 1Bor DCI 1D is different from the bit number for the first DCI, and doesnot equal to the value as shown in Table 4.

When the first DCI is DCI format 4, and one format of DCI {1, 2, 2A, 2B,2C, 2D} that is mapped onto the same searching space and used toschedule the second carrier has the same bit number as the first DCI, apadding bit having 0 value should be appended to the first DCI.

Table 5 is one embodiment according to the present invention. It isappreciated that when the uplink reference frame configuration of thesecond carrier is #1˜#6, the bit number of DCI 0/1A/1B/1D/4 is less thanthe corresponding bit number of the uplink reference frame configurationbeing as #0. The DCI coverage increase correspondingly by the DCIoverhead is saved. The bit number of the downlink-scheduling DCI inTable 5 is counted according to the payload size of the cross-carrierscheduling performed in the FDD system. That is it does not include TDDspecific bit.

TABLE 5 DCI bit number (with CIF, configured with a plurality ofcarriers) 1.4 MHz 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz Format 0/1A (Frame 2527 29 31 33 33 Configuration #1~#6) Format 1B (Frame 27 29 31 33 34 35Configuration #1~#6) Format 1D (Frame 27 29 31 33 34 35 Configuration#1~#6) Format 0/1A (Frame 27 29 31 33 34 35 Configuration #0) Format 1B(Frame 27 + 1 29 + 1 31 + 2 33 + 1 34 + 1 35 + 1 Configuration #0)Format 1D (Frame 27 + 1 29 + 1 31 + 2 33 + 1 34 + 1 35 + 1 Configuration#0) Format 1 22 25 30 34 36 42 Format 2 (2 tx) 34 37 42 46 48 54 Format2 (4 tx) 37 41 45 49 51 57 Format 2A (2 tx) 31 34 39 43 45 51 Format 2A(4 tx) 33 36 41 45 47 53 Format 2B 31 34 39 43 45 51 Format 2C 33 36 4145 47 53 Format 2D 35 38 43 47 49 55 Format 4 (Frame 36 37 + 1 40 42 4344 Configuration #0, 2tx) Format 4 (Frame 39 40 43 + 1 45 + 1 46 47Configuration #0, 4tx) Format 4 (Frame 34 + 1 35 38 40 41 42 + 1Configuration #1~#6, 2tx) Format 4 (Frame 37 + 1 38 + 1 41 + 1 43 44 45Configuration #1~#6, 4tx)

Preferably, the uplink reference frame configuration of the secondcarrier is configured by the SIB of the second carrier.

According to the transmission method used in UE for a TDD-FDD jointsystem, the method comprises the following steps:

Step A: receiving a second DCI on the first carrier, wherein the firstcarrier is the FDD downlink carrier, and the second DCI is thedownlink-scheduling DCI;

Step B: receiving downlink data on PDSCH in the second carrier accordingto the scheduling in the second DCI, wherein the second carrier is a TDDcarrier;

wherein the corresponding downlink DCI is counted according to thepayload size of the cross-carrier scheduling performed in the FDD systemfor the second carrier. That is the second DCI does not include TDDspecific bit.

According to the transmission method used in a system equipment for aTDD-FDD joint system, the method comprises the following steps:

Step A: transmitting a first DCI on the subframe n on a first carrier,wherein the first carrier is a FDD downlink carrier, n is an integer,and the first DCI is the uplink-scheduling DCI; and

Step B: receiving the uplink data on PUSCH of a second carrier in thesubframe n+k according to the scheduling of the first DCI, wherein thesecond carrier is a TDD carrier, k is the uplink scheduling delay of theuplink reference frame configuration of the second carrier on thesubframe n;

wherein for frame configuration #{0, 1, 2, 3, 4, 5, 6}, the first DCIcomprises the ULI/DAI bits only when the uplink reference frameconfiguration is #0. That is when the uplink reference frameconfiguration is frame configuration #0, the first DCI includes theULI/DAI bits; when the uplink reference frame configuration is one ofthe frame configuration #{1, 2, 3, 4, 5, 6}, the first DCI does notinclude the ULI/DAI bits.

Preferably, the Step A comprises the following Step A1, and the Step Bcomprises the following Step B1:

Step A1: in the jth subframe before the subframe n+k of the secondcarrier, transmitting at least one of the following:

PDSCH data;

PDCCH indicating SPS release;

EPDCCH indicating SPS release;

Step B1: receiving ACK/NACK associating with the Step A1 on the PUSCH;

wherein j is an uplink scheduling delay of the FDD system.

Preferably, the method further comprises the following step:

Step C: the higher layer transferring the ACK information (to thephysical layer) associating with the uplink data; and

Step D: Transmitting ACK or maintaining zero power in the correspondingPHICH resource in the sth subframe after the subframe n+k on the firstcarrier;

wherein the s is the PHICH reporting delay corresponding to the uplinkreference frame configuration.

Preferably, a padding bit of the first DCI is added according to the LTEscheme, wherein the corresponding downlink DCI is counted according tothe payload size of the cross-carrier scheduling performed in the FDDsystem for the second carrier.

Preferably, the uplink reference frame configuration of the secondcarrier is configured by the SIB of the second carrier.

According to the transmission method used in a system equipment for aTDD-FDD joint system, the method comprises the following steps:

Step A: transmitting a second DCI on the first carrier, wherein thefirst carrier is the FDD downlink carrier, and the second DCI is thedownlink-scheduling DCI;

Step B: transmitting downlink data on PDSCH in the second carrieraccording to the scheduling in the second DCI, wherein the secondcarrier is a TDD carrier;

wherein the corresponding downlink DCI is counted according to thepayload size of the cross-carrier scheduling performed in the FDD systemfor the second carrier.

According to the user equipment in the TDD-FDD combined system, the userequipment comprises:

a first module for receiving a first DCI on the subframe n on a firstcarrier, wherein the first carrier is a FDD downlink carrier, n is aninteger, and the first DCI is the uplink-scheduling DCI; and

a second module for transmitting the uplink data on PUSCH of a secondcarrier in the subframe n+k according to the scheduling of the firstDCI, wherein the second carrier is a TDD carrier, k is the uplinkscheduling delay of the uplink reference frame configuration of thesecond carrier on the subframe n;

wherein for frame configuration #{0, 1, 2, 3, 4, 5, 6}, the first DCIcomprises the ULI/DAI bits only when the uplink reference frameconfiguration is configuration #0.

According to the system equipment in the TDD-FDD joint system, thesystem equipment comprises:

a first module for transmitting a first DCI on the subframe n on a firstcarrier, wherein the first carrier is a FDD downlink carrier, n is aninteger, and the first DCI is the uplink-scheduling DCI; and

a second module for receiving the uplink data on PUSCH of a secondcarrier in the subframe n+k according to the scheduling of the firstDCI, wherein the second carrier is a TDD carrier, k is the uplinkscheduling delay of the uplink reference frame configuration of thesecond carrier on the subframe n;

wherein for frame configuration #{0, 1, 2, 3, 4, 5, 6}, the first DCIcomprises the ULI/DAI bits only when the uplink reference frameconfiguration is configuration #0.

The present invention solves the problem of DCI redundancy in thescenario that the FDD carrier is PCC and the TDD carrier is SCC. ThePUSCH scheduling complies with the TDD system timing, and the PDSCHscheduling complies with the FDD system timing. When the uplinkreference frame configuration of SCC is #1˜6, the uplink-scheduling DCIdoes not include ULI/DAI. It reduces the overhead of DCI redundancy, andincreases the DCI coverage. In the meanwhile, the present inventionmaintains the compatibility with the exiting system at upmost.

BRIEF DESCRIPTION OF THE DRAWINGS

The other features, objectives and advantages of certain exemplaryembodiments of the present invention will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a schematic diagram showing HARQ timing of the uplinkreference frame structure being as #0 according to one embodiment of thepresent invention;

FIG. 2 is a schematic diagram showing HARQ timing of the uplinkreference frame structure being as #1 according to one embodiment of thepresent invention;

FIG. 3 is a block diagram of a processing device sued in the UEaccording to one embodiment of the present invention; and

FIG. 4 is a block diagram of a processing device sued in the basestation according to one embodiment of the present invention.

In the drawings:

300 is user equipment;

301 is a first module of the user equipment;

302 is a second module of the user equipment;

400 is a system equipment;

401 is a first module of the system equipment; and

402 is a second module of the system equipment.

DETAILED DESCRIPTION

The following specific embodiments are provided to illustrate thepresent invention in details. The following embodiments will help tothose having ordinary skills in the art to further understand theinvention, but not limit the present invention in any forms. It shouldbe pointed out that, for those having ordinary skills in the art, thevarious modification and improvements may be conducted without departingfrom the spirit of the present invention. All of these belong to theprotection scope of the present invention.

Embodiment I

Embodiment I illustrates the HARQ timing when the uplink reference frameconfiguration is #0, as shown in FIG. 1. In FIG. 1, the first carrier isFDD downlink carrier: PCC, and the second carrier is TDD carrier: SCC.The second carrier is configured as frame configuration #0 through SIB.

For the UE, a first DCI—format #0 is received on the subframe 0 of thefirst carrier. The first carrier is FDD downlink carrier. The first DCIincludes two DIL bit information indicating the scheduled subframe issubframe 7 (as shown by the arrow S1). The uplink data is transmitted onPUSCH according to the scheduling of the first DCI on the subframe 7 ofthe second carrier. The second carrier is a TDD carrier.

For the base station, a first DCI—format #0 is transmitted on thesubframe 0 of the first carrier. The first carrier is FDD downlinkcarrier. The first DCI includes two DIL bit information indicating thescheduled subframe is subframe 7 (as shown by the arrow S1). The uplinkdata is received on PUSCH according to the scheduling of the first DCIon the subframe 7 of the second carrier. The second carrier is a TDDcarrier.

Embodiment II

Embodiment II illustrates the HARQ timing when the uplink referenceframe configuration is #1, as shown in FIG. 2. In FIG. 2, the firstcarrier is FDD downlink carrier: PCC, and the second carrier is TDDcarrier: SCC. The second carrier supports eIMTA: the first frame isframe configuration #2, and the second frame is frame configuration #1.The second carrier is configured as frame configuration #1 through RRCsignaling.

For the UE, a first DCI—format #4 is received on the subframe 1 of thefirst carrier. The first carrier is FDD downlink carrier. The first DCIdoes not include ULI/DAI bits. The uplink data is transmitted on PUSCHaccording to the scheduling of the first DCI on the subframe 7 of thefirst carrier according to the HARQ timing (as shown by the arrow S10)of frame configuration #1. The second carrier is a TDD carrier. Thecorresponding ACK/NACK is received on the subframe 1 of the second frameof the first carrier according the HARQ timing (as shown by the arrowS20) of frame configuration #1. When the UE receives EPDCCH or PDCCH orPDSCH from the first carrier or the second carrier on the fourthsubframe (as shown by the arrow U20) prior to the subframe 7, the UEtransmits corresponding uplink ACK/NACK on the subframe 7.

For the base station, a first DCI—format #4 is transmitted on thesubframe 1 of the first carrier. The first carrier is FDD downlinkcarrier. The first DCI does not include ULI/DAI bits. The uplink data isreceived on PUSCH according to the scheduling of the first DCI on thesubframe 7 of the first carrier according to the HARQ timing (as shownby the arrow S10) of frame configuration #1. The second carrier is a TDDcarrier. The corresponding ACK/NACK is transmitted on the subframe 1 ofthe second frame of the first carrier according the HARQ timing (asshown by the arrow S20) of frame configuration #1. When the base stationtransmits EPDCCH or PDCCH or PDSCH from the first carrier or the secondcarrier on the fourth subframe (as shown by the arrow U20) prior to thesubframe 7, the base station receives corresponding uplink ACK/NACK onthe subframe 7.

Embodiment III

Embodiment III is the block diagram of the processing device in the UE,as shown in FIG. 3. In FIG. 3, the UE processing device 300 comprises areceiving device 301 and a transmitting device 302.

The receiving device 301 receives a first DCI on the subframe n on afirst carrier. The first carrier is a FDD downlink carrier, n is aninteger, and the first DCI is the uplink-scheduling DCI. Thetransmitting device 302 transmits uplink data on PUSCH of a secondcarrier in the subframe n+k according to the scheduling of the firstDCI. The second carrier is a TDD carrier, k is the uplink schedulingdelay of the uplink reference frame configuration of the second carrieron the subframe n.

When the uplink reference frame configuration is frame configuration #0,the first DC includes the ULI/DAI bits. When the uplink reference frameconfiguration is one of the frame configuration #{1, 2, 3, 4, 5, 6}, thefirst DCI does not include the ULI/DAI bits.

Embodiment IV

Embodiment IV is the block diagram of the processing device in the basestation, as shown in FIG. 4. In FIG. 4, the eNB processing device 400comprises a transmitting device 401 and a receiving device 402.

The transmitting device 401 transmits a first DCI on the subframe n on afirst carrier. The first carrier is a FDD downlink carrier, n is aninteger, and the first DCI is the uplink-scheduling DCI. The receivingdevice 402 receives uplink data in the subframe n+k on a second carrieron PUSCH according to the scheduling of the first DCI. The secondcarrier is a TDD carrier, k is the uplink scheduling delay of the uplinkreference frame configuration of the second carrier on the subframe n.When the uplink reference frame configuration is one of the frameconfiguration #{1, 2, 3, 4, 5, 6}, the first DCI does not include theULI/DAI bits.

Those having ordinary skills in the art may understand all or part ofthe steps in the above method can be completed by the program toinstruction related hardware. The program can be stored in a computerreadable storage medium, such as a read-only memory, a hard disk or anoptical disk, etc. Optionally, all or part of the embodiment of theabove example can be implemented using one or more integrated circuits.Accordingly, each module unit of the embodiment can be realized in theform of hardware, and can be realized by the software function module,and the application is not limited to the combination of the softwareand the hardware of any particular form.

The present invention is illustrated and described with reference tospecific embodiment. It should be noted that the invention is notlimited to the specific implementation mentioned above. Those skilled inthe art may make various variation or modifications in the scope of theclaims. This does not affect the substance of the present invention.

What is claimed is:
 1. A transmission method used in UE for a TDD-FDDjoint system, comprising: Step A: receiving a first DCI on the subframen on a first carrier, wherein the first carrier is a FDD downlinkcarrier, n is an integer, and the first DCI is the uplink-schedulingDCI; and Step B: transmitting the uplink data on PUSCH of a secondcarrier in the subframe n+k according to the scheduling of the firstDCI, wherein the second carrier is a TDD carrier, k is the uplinkscheduling delay of the uplink reference frame configuration of thesecond carrier on the subframe n; wherein for frame configuration #{0,1, 2, 3, 4, 5, 6}, the first DCI comprises the ULI/DAI bits only whenthe uplink reference frame configuration is configuration #0.
 2. Thetransmission method used in UE for a TDD-FDD joint system according toclaim 1, wherein the Step A comprises the following step A1, and theStep B comprises the following Step B1: Step A1: in the jth subframebefore the subframe n+k of the second carrier, receiving at least one ofthe following: PDSCH data; PDCCH indicating SPS release; EPDCCHindicating SPS release; Step B1: transmitting ACK/NACK associating withthe Step A1 on the PUSCH; wherein j is an uplink scheduling delay of theFDD system.
 3. The transmission method used in UE for a TDD-FDD jointsystem according to claim 1, wherein the method comprises the followingsteps: Step C: for the uplink data, detecting the PHICH information inthe sth subframe after the subframe n+k on the first carrier, wherein sis the PHICH reporting delay corresponding to the uplink reference frameconfiguration; Step D: transferring ACK information to higher layerswhen the PHICH is detected as ACK, or when no PHICH is detected.
 4. Thetransmission method used in UE for a TDD-FDD joint system according toclaim 1, wherein a padding bit of the first DCI is added according tothe LTE scheme, wherein the corresponding downlink DCI is countedaccording to the payload size of the cross-carrier scheduling performedin the FDD system for the second carrier.
 5. The transmission methodused in UE for a TDD-FDD joint system according to claim 1, wherein theuplink reference frame configuration of the second carrier is configuredby the SIB of the second carrier.
 6. A method used in UE supportingTDD-FDD combined transmission, comprising: Step A: receiving a secondDCI on the first carrier, wherein the first carrier is the FDD downlinkcarrier, and the second DCI is the downlink-scheduling DCI; Step B:receiving downlink data on PDSCH in the second carrier according to thescheduling in the second DCI, wherein the second carrier is a TDDcarrier; wherein the corresponding downlink DCI is counted according tothe payload size of the cross-carrier scheduling performed in the FDDsystem for the second carrier.
 7. A transmission method used in a systemequipment for a TDD-FDD joint system, comprising: Step A: transmitting afirst DCI on the subframe n on a first carrier, wherein the firstcarrier is a FDD downlink carrier, n is an integer, and the first DCI isthe uplink-scheduling DCI; and Step B: receiving the uplink data onPUSCH of a second carrier in the subframe n+k according to thescheduling of the first DCI, wherein the second carrier is a TDDcarrier, k is the uplink scheduling delay of the uplink reference frameconfiguration of the second carrier on the subframe n; wherein for frameconfiguration #{0, 1, 2, 3, 4, 5, 6}, the first DCI comprises theULI/DAI bits only when the uplink reference frame configuration is frameconfiguration #0.
 8. The transmission method used in a system equipmentfor a TDD-FDD joint system according to claim 7, wherein the Step Acomprises the following Step A1, and the Step B comprises the followingStep B1: Step A1: in the jth subframe before the subframe n+k of thesecond carrier, transmitting at least one of the following: PDSCH data;PDCCH indicating SPS release; EPDCCH indicating SPS release; Step B1:receivingACK/NACK associating with the Step A1 on the PUSCH; wherein jis an uplink scheduling delay of the FDD system.
 9. The transmissionmethod used in a system equipment for a TDD-FDD joint system accordingto claim 7, wherein the method comprises the following steps: Step C:the higher layer transferring the ACK information associating with theuplink data; and Step D: Transmitting ACK or maintaining zero power inthe corresponding PHICH resource in the sth subframe after the subframen+k on the first carrier; wherein the s is the PHICH reporting delaycorresponding to the uplink reference frame configuration.
 10. Thetransmission method used in a system equipment for a TDD-FDD jointsystem according to claim 7, a padding bit of the first DCI is addedaccording to the LTE scheme, wherein the corresponding downlink DCI iscounted according to the payload size of the cross-carrier schedulingperformed in the FDD system for the second carrier.
 11. The transmissionmethod used in a system equipment for TDD-FDD joint system according toclaim 7, wherein the uplink reference frame configuration of the secondcarrier is configured by the SIB of the second carrier.
 12. Atransmission method used in a system equipment for TDD-FDD joint system,comprising: Step A: transmitting a second DCI on the first carrier,wherein the first carrier is the FDD downlink carrier, and the secondDCI is the downlink-scheduling DCI; Step B: transmitting downlink dataon PDSCH in the second carrier according to the scheduling in the secondDCI, wherein the second carrier is a TDD carrier; wherein thecorresponding downlink DCI is counted according to the payload size ofthe cross-carrier scheduling performed in the FDD system for the secondcarrier.
 13. A user equipment in the TDD-FDD joint system, comprising: afirst module for receiving a first DCI on the subframe n on a firstcarrier, wherein the first carrier is a FDD downlink carrier, n is aninteger, and the first DCI is the uplink-scheduling DCI; and a secondmodule for transmitting the uplink data on PUSCH of a second carrier inthe subframe n+k according to the scheduling of the first DCI, whereinthe second carrier is a TDD carrier, k is the uplink scheduling delay ofthe uplink reference frame configuration of the second carrier on thesubframe n; wherein for frame configuration #{0, 1, 2, 3, 4, 5, 6}, thefirst DCI comprises the ULI/DAI bits only when the uplink referenceframe configuration is configuration #0.
 14. A system equipment in theTDD-FDD joint system, comprising: a first module for transmitting afirst DCI on the subframe n on a first carrier, wherein the firstcarrier is a FDD downlink carrier, n is an integer, and the first DCI isthe uplink-scheduling DCI; and a second module for receiving the uplinkdata on PUSCH of a second carrier in the subframe n+k according to thescheduling of the first DCI, wherein the second carrier is a TDDcarrier, k is the uplink scheduling delay of the uplink reference frameconfiguration of the second carrier on the subframe n; wherein for frameconfiguration #{0, 1, 2, 3, 4, 5, 6}, the first DCI comprises theULI/DAI bits only when the uplink reference frame configuration isconfiguration #0.